Releasing space allocated to a space efficient target storage in a copy relationship with a source storage

ABSTRACT

Provided are a computer program product, system, and method for releasing space allocated to a space efficient target storage in a copy relationship with a source storage. Source and target copy relationships indicate source data in the source storage to copy to target data in the target storage. The source copy relationship indicates source data that need to be copied to the target data before being updated, and the target copy relationship indicates target data tracks updated with data copied from corresponding source data. An operation is initiated that results in terminating the source and target copy relationships. Space allocated to the target data for the source and target copy relationships is released in response to determining that the target storage comprises the space efficient storage. The source and target copy relationships are removed.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a computer program product, system, andmethod for releasing space allocated to a space efficient target storagein a copy relationship with a source storage.

2. Description of the Related Art

In a storage environment, a storage controller may create point-in-time(“PiT”) copies of a production volume using point-in-time copytechniques, such as the IBM FlashCopy® (FlashCopy is a registeredtrademark of IBM), snapshot, etc. A point-in-time copy replicates datain a manner that appears instantaneous and allows a host to continueaccessing the source volume while actual data transfers to the copyvolume are deferred to a later time. The point-in-time copy appearsinstantaneous because Input/Output (“I/O”) complete is returned to thecopy operation in response to generating the relationship datastructures without copying the data from the source to the targetvolumes. Point-in-time copy techniques typically defer the transfer ofthe data in the source volume at the time the point-in-time copyrelationship was established to the copy target volume until a writeoperation is requested to that data block on the source volume. Datatransfers may also proceed as a background copy process with minimalimpact on system performance. The point-in-time copy relationships thatare immediately established in response to the point-in-time copycommand include a bitmap or other data structure indicating the locationof blocks in the volume at either the source volume or the copy volume.The point-in-time copy comprises the combination of the data in thesource volume and the data to be overwritten by the updates transferredto the target volume.

In a space efficient volume, volumes are thinly provisioned which meansthat physical storage space is not allocated to the volumes until awrite to the volumes requires the space. The amount of space that isallocated is based on the amount of data that is written to the volume.In space efficient volumes, the device capacity for the devices assignedto the repository pool exceeds the physical addresses allocated to thevolumes.

In space efficient volumes, when a point-in-time copy operation isperformed, physical storage space is allocated only when a writeoperation is performed as part of the copying of the point-in-time datafrom the source storage to the target storage so that data is allocatedto the target storage when needed for a specific transfer that isoccurring.

When withdrawing point-in-time copy relationships, if the customer doesnot specify to release space as part of the withdrawal operation, thespace allocated to a space efficient, i.e., thinly provisioned, targetvolume/dataset will remain allocated. If the copying of all the sourcetracks to the target tracks has not completed for the copy relationship,then the target volume/dataset is not useable (even though the space isstill allocated).

The IBM FlashCopy® point-in-time copy functions provide a Fast ReverseRestore operation, which copies the target tracks to which the sourcetracks were copied in a FlashCopy pair back to the source tracks fromwhich they were copied when a Fast Reverse Restore relationship isenabled. The Fast Reverse Restore operation may be performed after aplanned or unplanned outage.

There is a need in the art for improved techniques for managingspace-efficient target volumes in a point-in-time copy relationship whenthe copy relationship is terminated.

SUMMARY

Provided are a computer program product, system, and method forreleasing space allocated to a space efficient target storage in a copyrelationship with a source storage. Source and target copy relationshipsindicate source data in the source storage to copy to target data in thetarget storage. The source copy relationship indicates source data thatneed to be copied to the target data before being updated, and thetarget copy relationship indicates target data tracks updated with datacopied from corresponding source data. An operation is initiated thatresults in terminating the source and target copy relationships. Adetermination is made as to whether the target storage comprises a spaceefficient storage in response to initiating the operation that resultsin terminating the source and target copy relationships. In the spaceefficient storage, physical storage space is allocated to the targetdata when required to store data submitted to the source data. Spaceallocated to the target data for the source and target copyrelationships is released in response to determining that the targetstorage comprises the space efficient storage. The source and targetcopy relationships are removed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a storage environment.

FIG. 2 illustrates an embodiment of a copy relationship.

FIG. 3 illustrates an embodiment of operations that result interminating source and target copy relationships.

FIG. 4 illustrates an embodiment of operations to withdraw source andtarget copy relationships for a copy relationship pair.

FIG. 5 illustrates an embodiment of operations to restore source datafrom target data in a point-in-time copy relationship.

FIG. 6 illustrates a computing environment in which the components ofFIG. 1 may be implemented.

DETAILED DESCRIPTION

When a point-in-time copy relationship is terminated or withdrawn as aresult of an explicit withdrawal command or as a result of a restoreoperation, space allocated to a space efficient, e.g., thinlyprovisioned, source volume may remain provisioned after the copyrelationship is ended. Further, if not all the data from the sourcevolume in the copy relationship was copied over to the target volume,than the copy at the target volume may not be usable, and the spaceallocated to store that partial copy of the source volume on the targetmay be otherwise unusable and unavailable to assign to otherspace-efficient volumes in the target storage. The target volume mayonly include a partial copy of the source volume if the copyrelationship was established with a parameter specifying that there isno background copy of all the source data, such that only source datathat is updated is copied over to the target volume before it isupdated.

Described embodiments provide techniques to automatically release thestorage space allocated to a target volume in a copy relationship byperforming operations to release the space allocated to the targetvolume when initiating an operation that will result in termination ofthe copy relationship when the target storage having the target data forthe copy relationship to be terminated comprises space efficientstorage.

FIG. 1 illustrates an embodiment of a data storage environment having asource 100 _(S) and target 100 _(T) storage controllers managing accessto source 102 _(S) and target 102 _(T) volumes configured in a source104 _(S) and target 104 _(T) storage system, respectively. Host systems106 perform read and write operations with respect to the volumes 102over a network 108. The source 100 _(S) and target 100 _(T) storagecontrollers each respectively include an operating system 110 _(S), 110_(T) to manage I/O requests from the host systems 106 with respect tothe volumes 102 _(S), 102 _(T). The operating system 110 _(S), 110 _(T)may configure the volumes 102 _(S), 102 _(T) in the storages 104 _(S),104 _(T), where data is stored in data units, such as tracks, logicalblock addresses (LBAs), extents, etc. An extent comprises a grouping oftracks, blocks or other data units that is assigned to volumes 102 _(S),102 _(T).

The storage systems 104 _(S), 104 _(T) may comprise different types orclasses of storage devices, such as magnetic hard disk drives, solidstate storage device (SSD) comprised of solid state electronics, EEPROM(Electrically Erasable Programmable Read-Only Memory), flash memory,flash disk, Random Access Memory (RAM) drive, storage-class memory(SCM), etc., Phase Change Memory (PCM), resistive random access memory(RRAM), spin transfer torque memory (STM-RAM), conductive bridging RAM(CBRAM), magnetic hard disk drive, optical disk, tape, etc. The volumes102 _(S), 102 _(T) may further be configured from an array of devices,such as Just a Bunch of Disks (JBOD), Direct Access Storage Device(DASD), Redundant Array of Independent Disks (RAID) array,virtualization device, etc. Further, the storages 104 _(S), 104 _(T) maycomprise heterogeneous storage devices from different vendors anddifferent types of storage devices, such as a first type of storagedevices, e.g., hard disk drives, that have a slower data transfer ratethan a second type of storage devices, e.g., SSDs.

The network 108 may comprise a network such as one or moreinterconnected Local Area Networks (LAN), Storage Area Networks (SAN),Wide Area Network (WAN), peer-to-peer network, wireless network, etc.

The host 106 includes a copy manager program 114 _(H) to generaterequests to create point-in-time copies of source volumes 102 _(S) totarget volumes 102 _(T) by submitting a point-in-time copy establishrequest to the source 114 _(S) and target 114 _(T) copy managers at thestorage controllers 100 _(S), 100 _(T). The point-in-time copies aredefined in copy relationships 200 _(H), 200 _(S), 200 _(T), maintainedin the host 106 and storage controllers 100 _(S), 100 _(T).

The storage controllers 100 _(S), 100 _(T) include point-in-time copymanagers 114 _(S), 114 _(T) to create point-in-time copies of the sourcedata 102 _(S), e.g., FlashCopy, snapshot, etc., in response to PiT copyestablish requests from the host system 106 copy manager 114 _(H). Whencreating a PiT copy, the source storage controller copy manager 114 _(S)generates PiT copy information in a copy relationships 200 _(S) on thePiT copy created as of a point-in-time and the target copy manager 114_(T) creates corresponding target copy relationship 200 _(T) for thetarget of the copy relationship 200 _(S), 200 _(T). Thus, a source 200_(S) and target 200 _(T) copy relationship pair are created for apoint-in-time copy to establish.

The copy managers 114 _(S), 114 _(T) perform a PiT copy operation thatreplicates data in a manner that appears instantaneous and allowsprocesses to continue accessing the source volume 102 _(S) while actualdata transfers to the copy volume are deferred to a later time, such aswhen the source data 102 _(S) is updated. The point-in-time copy appearsinstantaneous because the storage controller copy manager 114 _(S)returns I/O complete to the host PiT copy establish request in responseto generating the relationship data structures without copying the data.

In certain embodiments, the operating systems 110 _(S), 110 _(T) maymanage volumes 102 _(S), 102 _(T) as space efficient volumes, where thevolumes 102 _(S), 102 _(T) are configured without allocating actualstorage space in the storage system 104 until the space is needed fordata written to the volumes 102 _(S), 102 _(T). In this way the volumesare “thin provisioned” because space is not allocated until needed forwrite data. Volumes 102 _(S), 102 _(T) configured as space efficientvolumes are initially virtual volumes because space in the storagesystem 104 _(S), 104 _(T) has not yet been allocated.

The operating systems 110 _(S), 110 _(T) each maintain an extent pool116 _(S), 116 _(T) of free extents of tracks available to assign to thevolumes 102 _(S), 102 _(T) configured as thin-provisioned or spaceefficient volumes when space is needed.

The operating systems 110 _(S), 110 _(T) each respectively maintainvolume tables 118 _(S), 118 _(T) providing information on the configuredvolumes 102 _(S), 102 _(T), including a mapping of logical to physicaladdresses. When a space efficient volume 102 _(S), 102 _(T) is firstprovisioned, all the logical addresses are defined in the volume table118 _(S), 118 _(T), but the mapping of physical storage space in thestorage system 104 _(S), 104 _(T) to the logical addresses is not yetprovisioned until a write occurs to the logical addresses.

FIG. 2 illustrates an instance of a copy relationship 200 _(i), such ascopy relationships 200 _(S), 200 _(T), and 200 _(H). A PiT copyrelationship instance 200 _(i) may include a PiT copy identifier 202identifying the PiT copy created by the copy manager 114 _(i) (i.e., 114_(H), 114 _(S), 114 _(T)) at the storage controller 100; a point-in-time204 of the PiT copy 202, which may mean that data is consistent as ofthat point-in-time 204; source data 206, e.g., source volume 102 _(S),from which data is copied; target data 208, e.g., target volume 102_(T), to which the PiT data is copied; change information 210 indicatingwhich data or tracks in the source data 206 has changed since thepoint-in-time 204 and while the PiT copy 202 was open; and a withdrawpending flag 212 indicating whether a withdrawal operation isin-progress of being performed to terminate the copy relationship 200_(i). The change information 210 may comprise a bitmap having a bit foreach data unit (e.g., track) that is set to one of two values indicatingthe data or track represented by the bit has or has not been updatedsince the point-in-time 204. Initially, the change information 210 forall the source data is set to indicate not copied or changed, and then abit is reset when the track or data unit represented by the changeinformation 210 is copied from the source storage to the target storage.The source 206 and target 208 data may comprise a volume, a subset of avolume or other unit of data.

When establishing a copy relationship between a source volume 102 _(S)and a target volume 102 _(T), a pair of copy relationships 200 _(S), 200_(T) are created each indicating the same point-in-time 204, source data(e.g., source volume) 206, and target data 208 (e.g., target volume).The change information 210 for the source copy relationship 200 _(S) mayindicate source data or tracks in the source data 206 that have not beencopied over to the target data 208. The source change information 210_(S) may initially indicate that all tracks or data units in the sourcedata unit 206 need to be copied, the change information 210 for a trackor data unit is changed when the source data or source track as of thepoint-in-time is copied over before the update to the source track. Thetarget change information 210 _(T) in the target copy relationship 200_(T) identifies each target track or data unit in the target data 208that has a copy of the source data before being updated.

In described embodiments, the target data or volume 208 may comprise aspace efficient storage or volume, such as a thinly provisioned volumewhere extents of data from the extent pool 116 _(T) are only provisionedwhen needed for data being copied from the source tracks 206. Further,in certain embodiments, the copy relationship may comprise a “no copy”copy relationship where all the source data 206 is not copied to thetarget data 208 as part of a background copy operation. Instead, thesource data as of the point-in-time is only copied before being changedby a write to the source data 208.

FIG. 3 illustrates an embodiment of operations performed by at least oneof the copy managers 114 _(i), such as at least one of 114 _(H), 114_(S), 114 _(T), to release extents allocated to the space efficienttarget volume 102 _(T) in a copy relationship pair 200 _(S), 200 _(T)for one copy relationship being terminated. Upon initiating an operationto terminate the source and target copy relationship pair 200 _(S), 200_(T), the copy manager 114 _(i) determines (at block 302) whether thetarget data 208 comprises a space efficient storage, such as a spaceefficient or thin volume. If (at block 302) the target storage 104 _(T)including the target data 208 (volume) is space efficient, then adetermination is made (at block 303) whether all the source data 206 hasbeen copied to the target data 208. If not, then Input/Output (I/O)requests to the target data 208 are quiesced (at block 306), such as bythe target operating system 110 _(T), and the space, such as extents,allocated to the target data 208 for the source and copy relationships,are released (at block 308), and returned to the target extent pool 116_(T), where they are available for further allocation to a spaceefficient target volume 102 _(T). After releasing the space, I/O isunquiesced (at block 310) to allow writes to proceed to the target data208 and the source 200 _(S) and target 200 _(T) copy relationships areremoved (at block 312). If (at block 302) the target storage 104 _(T) isnot space efficient or if (at block 303) all the source data 206 hasbeen copied to target data 208, then the copy relationships 200 _(S),200 _(T) are terminated and removed (at block 304).

FIG. 4 illustrates an embodiment of operations performed by the at leastone of the copy managers 114 _(i), e.g., 114 _(H), 114 _(S), 114 _(T),to withdraw a copy relationship. Upon initiating (at block 400)operation to withdraw a source 200 _(S) and target 200 _(T) copyrelationship pair, the withdraw pending 212 flags in the copyrelationship pairs 200 _(S), 200 _(T) to remove are set (at block 402)to indicate withdraw pending. If (at block 404) the target storage 104_(T) having the target data 208, e.g., target volume 102 _(T), comprisesa space efficient storage, then a determination is made (at block 406)if all the source data 206 in the source 200 _(S) and target 200 _(T)copy relationship has been copied to corresponding target data, e.g.,tracks. This may be determined by checking whether the target changeinformation 210 _(T) indicates that not all of the target data unitshave received data from the corresponding source data units, e.g.,tracks, which may occur when the copy relationships 200 _(S) and 200_(T) are “no copy” background relationships where the source data 206 isnot copied in full in the background to the target data 208.

If (at block 406) not all the source data 206, as of the point-in-time204, has been copied over, then I/O to the target data 208 is quiesced(at block 408) and the space, i.e., extents, allocated to the targetdata 208 for the source and copy relationships 200 _(S), 200 _(T) arereleased and returned to the target extent pool 116 _(T). Afterreleasing the space, I/O is unquiesced (at block 412) to allow writes toproceed to the target data, and the source 200 _(S) and target 200 _(T)copy relationships are removed (at block 414). If (from the no branch atblock 404) the target storage 104 _(T) does not comprise space efficientstorage or if (from the yes branch at block 406) all the source data 206has been copied to the target data 208, then the copy relationships 200_(S) and 200 _(T) are terminated (at block 416).

With the operations of FIG. 4, the space allocated to a space efficienttarget volume is automatically released when withdrawing the copyrelationships when the target data 208 does not include a full copy ofthe source data 206. If the target data does not include a full copy,then it is not useful to retain the partial copy of the source data atthe target data 208, and the extents used for the target data arereleased to make available for other space efficient volumes at thetarget storage 104 _(T).

FIG. 5 illustrates an embodiment of operations performed by the at leastone of the copy managers 114 _(i), i.e., 114 _(H), 114 _(S), 114 _(T),to perform a restore to the source data 102 _(S) (e.g., volume) from thetarget data 102 _(T) (e.g., volume) in a copy relationship pair 200_(S), 200 _(T). The restore operation may be performed when informationon changes to the target data 102 _(T) is recorded in target changeinformation 210 _(T) and there is no background copy. The restoreoperation may be performed after a planned or unplanned outage at thesource 100 _(s). Upon initiating (at block 500) a restore operation fromthe target data 208 to the source data 206 of a copy relationship pair200 _(S), 200 _(T), the copy manager 114 _(S), 114 _(T) reverses (atblock 502) the source 200 _(S) and target 200 _(T) copy relationships bymodifying the source 200 _(S) and target 200 _(T) copy relationships toproduce new source 102 _(S)′ and new target 102 _(T)′ copy relationshipswhere the source data comprises new target data and the target datacomprises a new source data. The copy manager 114 _(T) copies (at block504) tracks in the new source data 102 _(S)′ (old target data 102 _(T)indicated in target change information 210 as changed, i.e., copied overfrom the source) back to the new target data 102 _(T)′ (old source data102 _(S)). In this way, the source data 102 _(S) is restored to thepoint-in-time 204 state. After copying the target tracks back to thesource data 102 _(S) the new target copy relationship 200 _(T)′ (fromthe new source data to new target data) is removed (at block 506).

If (at block 508) the new source storage, i.e., target storage 102 _(T),of the copy relationship pair comprise a space efficient storage, thenthe copy manager 114 _(T) quiesces (at block 510) I/O to the new sourcestorage (e.g., new source (target) volume 102 _(T)) and the space, i.e.,extents, allocated to the target data 208 for the source and copyrelationships 200 _(S), 200 _(T) is released (at block 512) and returnedto the target extent pool 116 _(T). After releasing the space, I/O isunquiesced (at block 514) to allow writes to proceed to the new source(target) data, and the new source 200 _(S)′ (modified old target copyrelationship 200 _(T)) is removed (at block 516). If (at block 508) thenew source target storage 104 _(T) is not a space efficient storage,then the copy relationships 200 _(S), 200 _(T) are terminated.

With the operations of FIG. 5, if a restore is performed from a targetstorage that comprises a space efficient storage, then after copyingback the target data, comprising source data copied over as of thepoint-in-time of the copy relationship, to the source data, the spaceallocated to the space efficient target storage may be released andreturned to an extent pool. Described embodiments allow the spaceallocated to the target data to be returned to the extent pool to beavailable for further provisioning in the case that the source data isrestored from the target data to be at the point-in-time of the copyrelationships.

The reference characters used herein, such as i, are used to denote avariable number of instances of an element, which may represent the sameor different values, and may represent the same or different value whenused with different or the same elements in different describedinstances.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The computational components of FIG. 1, including the storagecontrollers 100 _(S), 100 _(T) and host 106 may be implemented in one ormore computer systems, such as the computer system 602 shown in FIG. 6.Computer system/server 602 may be described in the general context ofcomputer system executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 602 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 6, the computer system/server 602 is shown in the formof a general-purpose computing device. The components of computersystem/server 602 may include, but are not limited to, one or moreprocessors or processing units 604, a system memory 606, and a bus 608that couples various system components including system memory 606 toprocessor 604. Bus 608 represents one or more of any of several types ofbus structures, including a memory bus or memory controller, aperipheral bus, an accelerated graphics port, and a processor or localbus using any of a variety of bus architectures. By way of example, andnot limitation, such architectures include Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 602 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 602, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 606 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 610 and/or cachememory 612. Computer system/server 602 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 613 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 608 by one or more datamedia interfaces. As will be further depicted and described below,memory 606 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 614, having a set (at least one) of program modules 616,may be stored in memory 606 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. The components of the computer 602 may be implemented asprogram modules 616 which generally carry out the functions and/ormethodologies of embodiments of the invention as described herein. Thesystems of FIG. 1 may be implemented in one or more computer systems602, where if they are implemented in multiple computer systems 602,then the computer systems may communicate over a network.

Computer system/server 602 may also communicate with one or moreexternal devices 618 such as a keyboard, a pointing device, a display620, etc.; one or more devices that enable a user to interact withcomputer system/server 602; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 602 to communicate withone or more other computing devices. Such communication can occur viaInput/Output (I/O) interfaces 622. Still yet, computer system/server 602can communicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 624. As depicted, network adapter 624communicates with the other components of computer system/server 602 viabus 608. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 602. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims herein after appended.

What is claimed is:
 1. A computer program product for managing copyrelationships between a source storage and a target storage, wherein thecomputer program product comprises a computer readable storage mediumhaving program instructions embodied therewith, the program instructionsexecutable by a processor to cause operations, the operationscomprising: providing a source and target copy relationships indicatingsource data in the source storage to copy to target data in the targetstorage, wherein the source copy relationship indicates source data thatneeds to be copied to the target data before being updated, and whereinthe target copy relationship indicates target data tracks updated withdata copied from corresponding source data; initiating an operation thatresults in terminating the source and target copy relationships;determining whether the target storage comprises a space efficientstorage in response to initiating the operation that results interminating the source and target copy relationships, wherein in thespace efficient storage, physical storage space is allocated to thetarget data when required to store data submitted to the source data;releasing space allocated to the target data for the source and targetcopy relationships in response to determining that the target storagecomprises the space efficient storage; and removing the source andtarget copy relationships.
 2. The computer program product of claim 1,wherein the initiating the operation that results in terminatingcomprises initiating an operation to withdraw the source and target copyrelationships, wherein the operations further comprise: determiningwhether all the source data in the source and target copy relationshipshas been copied to the target data in response to initiating theoperation to withdraw the source and target copy relationships, whereinthe releasing the space is performed in response to determining boththat not all the source data in the source and target copy relationshipshas been copied to the target data and that the target storage comprisesthe space efficient storage.
 3. The computer program product of claim 2,wherein the source and target copy relationships are removed in responseto the releasing the space allocated to the target storage.
 4. Thecomputer program product of claim 2, wherein the operations furthercomprise: quiescing input/output (I/O) operations to the target data inresponse to determining that the target storage comprises the spaceefficient storage, wherein the releasing the space allocated to thetarget data is performed in response to quiescing the I/O operations;unquiescing I/O operations to allow I/O operations to proceed to thetarget data in response to releasing the space allocated to the targetdata; and removing the source and target copy relationships in responseto unquiescing the I/O operations.
 5. The computer program product ofclaim 1, wherein the initiating the operation that results interminating comprises a restore operation, wherein the operationsfurther comprise: copying data in target data to which data from thesource data was copied, according to the target copy relationship, backto the source data from which the data was copied, wherein thedetermining whether the target storage comprises the space efficientstorage is performed in response to completing the copying the data inthe target data to the source data from which the data was copied. 6.The computer program product of claim 5, wherein the operations furthercomprise: reversing the source and target copy relationships bymodifying the source and target copy relationships to be new source andtarget copy relationships where the source storage comprises a newtarget storage and the target storage comprises a new source storage,wherein the copying of the target data to the source data is performedas part of the new source and new target copy relationships.
 7. Thecomputer program product of claim 6, further comprising: removing thenew target copy relationship, wherein the determining whether the targetstorage comprises the space efficient storage and releasing spaceallocated to the new source storage are performed after removing the newtarget copy relationship; and removing the new source copy relationshipafter releasing the space allocated to the target storage.
 8. Thecomputer program product of claim 7, wherein the operations furthercomprise: quiescing Input/Output (I/O) operations to the target data inresponse to removing the new target copy relationship, wherein the spaceallocated to the target data is released in response to quiescing theI/O operations; and unquiescing I/O operations to the target data inresponse to releasing the space allocated to the target data, whereinthe new source copy relationship is removed after the unquiescing theI/O operations.
 9. A system for managing copy relationships between asource storage and a target storage, comprising: a processor; and acomputer readable storage medium having program instructions executed bythe processor to cause operations, the operations comprising: providinga source and target copy relationships indicating source data in thesource storage to copy to target data in the target storage, wherein thesource copy relationship indicates source data that needs to be copiedto the target data before being updated, and wherein the target copyrelationship indicates target data tracks updated with data copied fromcorresponding source data; initiating an operation that results interminating the source and target copy relationships; determiningwhether the target storage comprises a space efficient storage inresponse to initiating the operation that results in terminating thesource and target copy relationships, wherein in the space efficientstorage, physical storage space is allocated to the target data whenrequired to store data submitted to the source data; releasing spaceallocated to the target data for the source and target copyrelationships in response to determining that the target storagecomprises the space efficient storage; and removing the source andtarget copy relationships.
 10. The system of claim 9, wherein theinitiating the operation that results in terminating comprisesinitiating an operation to withdraw the source and target copyrelationships, wherein the operations further comprise: determiningwhether all the source data in the source and target copy relationshipshas been copied to the target data in response to initiating theoperation to withdraw the source and target copy relationships, whereinthe releasing the space is performed in response to determining boththat not all the source data in the source and target copy relationshipshas been copied to the target data and that the target storage comprisesthe space efficient storage.
 11. The system of claim 10, wherein thesource and target copy relationships are removed in response to thereleasing the space allocated to the target storage.
 12. The system ofclaim 9, wherein the initiating the operation that results interminating comprises a restore operation, wherein the operationsfurther comprise: copying data in target data to which data from thesource data was copied, according to the target copy relationship, backto the source data from which the data was copied, wherein thedetermining whether the target storage comprises the space efficientstorage is performed in response to completing the copying the data inthe target data to the source data from which the data was copied. 13.The system of claim 12, wherein the operations further comprise:reversing the source and target copy relationships by modifying thesource and target copy relationships to be new source and target copyrelationships where the source storage comprises a new target storageand the target storage comprises a new source storage, wherein thecopying of the target data to the source data is performed as part ofthe new source and new target copy relationships.
 14. The system ofclaim 13, further comprising: removing the new target copy relationship,wherein the determining whether the target storage comprises the spaceefficient storage and releasing space allocated to the new sourcestorage are performed after removing the new target copy relationship;and removing the new source copy relationship after releasing the spaceallocated to the target storage.
 15. A method for managing copyrelationships between a source storage and a target storage, comprising:providing a source and target copy relationships indicating source datain the source storage to copy to target data in the target storage,wherein the source copy relationship indicates source data that needs tobe copied to the target data before being updated, and wherein thetarget copy relationship indicates target data tracks updated with datacopied from corresponding source data; initiating an operation thatresults in terminating the source and target copy relationships;determining whether the target storage comprises a space efficientstorage in response to initiating the operation that results interminating the source and target copy relationships, wherein in thespace efficient storage, physical storage space is allocated to thetarget data when required to store data submitted to the source data;releasing space allocated to the target data for the source and targetcopy relationships in response to determining that the target storagecomprises the space efficient storage; and removing the source andtarget copy relationships.
 16. The method of claim 15, wherein theinitiating the operation comprises initiating an operation to withdrawthe source and target copy relationships, further comprising:determining whether all the source data in the source and target copyrelationships has been copied to the target data in response toinitiating the operation to withdraw the source and target copyrelationships, wherein the releasing the space is performed in responseto determining both that not all the source data in the source andtarget copy relationships has been copied to the target data and thatthe target storage comprises the space efficient storage.
 17. The methodof claim 16, wherein the source and target copy relationships areremoved in response to the releasing the space allocated to the targetstorage.
 18. The method of claim 15, wherein the initiating theoperation comprises a restore operation, further comprising: copyingdata in target data to which data from the source data was copied,according to the target copy relationship, back to the source data fromwhich the data was copied, wherein the determining whether the targetstorage comprises the space efficient storage is performed in responseto completing the copying the data in the target data to the source datafrom which the data was copied.
 19. The method of claim 18, furthercomprising: reversing the source and target copy relationships bymodifying the source and target copy relationships to be new source andtarget copy relationships where the source storage comprises a newtarget storage and the target storage comprises a new source storage,wherein the copying of the target data to the source data is performedas part of the new source and new target copy relationships.
 20. Themethod of claim 19, further comprising: removing the new target copyrelationship, wherein the determining whether the target storagecomprises the space efficient storage and releasing space allocated tothe new source storage are performed after removing the new target copyrelationship; and removing the new source copy relationship afterreleasing the space allocated to the target storage.